Skip to content

WIP: Multipart index single field query #169

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

olegrok
Copy link
Contributor

@olegrok olegrok commented Jun 15, 2021

Only tests from this patch have value. This patch can't be merged as is because introduces performance degradation.

Expected that {0, 1}, {0, 2} will be returned. But rowset is
empty.
@olegrok olegrok force-pushed the multipart-index-single-field-query branch from 7cfdb86 to c64ffa8 Compare June 15, 2021 18:41
@olegrok olegrok force-pushed the multipart-index-single-field-query branch from c64ffa8 to 862906c Compare June 15, 2021 19:19
Comment on lines -56 to -61
local cmp_operator = select_comparators.get_cmp_operator(opts.tarantool_iter)
local scan_comparator = select_comparators.gen_tuples_comparator(cmp_operator, index.parts)
local after_tuple_key = utils.extract_key(opts.after_tuple, index.parts)
if scan_comparator(after_tuple_key, opts.scan_value) then
value = after_tuple_key
end
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually after this change scroll_to_after_tuple makes fullscan. So funny that our tests don't catch it.

@olegrok
Copy link
Contributor Author

olegrok commented Jun 30, 2021

Will be fixed in #177

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant